Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9dbf1cf53f7a6fc5793ffc0f43897c25e1fa86b3b023bae4bcfb097cf1965153

Tx prefix hash: 7a60a75b59ea0c1d24fe5296fae7a55616fd7f05dd7c09de5e5880b797980fec
Tx public key: a317eb4509efe0dc7a77a581df1a7b06d38df1aab153876e91abc4e38a15bcbe
Timestamp: 1726978460 Timestamp [UCT]: 2024-09-22 04:14:20 Age [y:d:h:m:s]: 00:110:09:14:00
Block: 1115411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78926 RingCT/type: yes/0
Extra: 01a317eb4509efe0dc7a77a581df1a7b06d38df1aab153876e91abc4e38a15bcbe021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb85577590d83a85de26fa52ddedb6ec536151b180f17ae66a844cd95720969 0.600000000000 1595534 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1115421, "vin": [ { "gen": { "height": 1115411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb85577590d83a85de26fa52ddedb6ec536151b180f17ae66a844cd95720969" } } ], "extra": [ 1, 163, 23, 235, 69, 9, 239, 224, 220, 122, 119, 165, 129, 223, 26, 123, 6, 211, 141, 241, 170, 177, 83, 135, 110, 145, 171, 196, 227, 138, 21, 188, 190, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8