Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526cd5b9c20912d5116d2d32848126c6a1f6005a0093cd1738248645ec851683

Tx prefix hash: a7c68c5e5bd059809a59880ccd95dd89c6145c67efa07777b51917e91339cc60
Tx public key: aa984dafebe079d4656f9fafd3beef830f52c1e52d02cbdcecc7d9cb69fe2119
Timestamp: 1719105359 Timestamp [UCT]: 2024-06-23 01:15:59 Age [y:d:h:m:s]: 00:283:21:11:39
Block: 1050120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202863 RingCT/type: yes/0
Extra: 01aa984dafebe079d4656f9fafd3beef830f52c1e52d02cbdcecc7d9cb69fe211902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8622c423fecc795e55f2ba27ae4f80bb25e2cc954c8f01de6f289ae6a8d560c1 0.600000000000 1520279 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": 1050130, "vin": [ { "gen": { "height": 1050120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8622c423fecc795e55f2ba27ae4f80bb25e2cc954c8f01de6f289ae6a8d560c1" } } ], "extra": [ 1, 170, 152, 77, 175, 235, 224, 121, 212, 101, 111, 159, 175, 211, 190, 239, 131, 15, 82, 193, 229, 45, 2, 203, 220, 236, 199, 217, 203, 105, 254, 33, 25, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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