Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a4cffe558f4e8a1063caaa25f2d72b7bc8ebf0a6bee9f0bdd3f3f30492e1f3

Tx prefix hash: e9149d447484e27bdcb402b821c915ee0412e4df23ec5924576ba57a2413a8ec
Tx public key: 0570c524259ab85769a988ef97646bdc687e2c2053fb00275b6c4ba9f9c054dd
Timestamp: 1720069668 Timestamp [UCT]: 2024-07-04 05:07:48 Age [y:d:h:m:s]: 00:172:00:45:05
Block: 1058124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123144 RingCT/type: yes/0
Extra: 010570c524259ab85769a988ef97646bdc687e2c2053fb00275b6c4ba9f9c054dd0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddc696270b1fa77bc6ca7b050d64d11a8ad196c2f6515be3038eba7388df7d70 0.600000000000 1528573 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": 1058134, "vin": [ { "gen": { "height": 1058124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddc696270b1fa77bc6ca7b050d64d11a8ad196c2f6515be3038eba7388df7d70" } } ], "extra": [ 1, 5, 112, 197, 36, 37, 154, 184, 87, 105, 169, 136, 239, 151, 100, 107, 220, 104, 126, 44, 32, 83, 251, 0, 39, 91, 108, 75, 169, 249, 192, 84, 221, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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