Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b96f57fd7d95db7cf2f847bb17429c061766ec54e696bd8aafa76783bd6e8c

Tx prefix hash: 8d72cad2d3a534e69758b0e58e9ffac36a55ef43df43d3011afb16ae918e5350
Tx public key: 9072c97bbdf872324f1fdbb5eb912636098e51d2f61e5403306b1c2397ddadc7
Timestamp: 1702712464 Timestamp [UCT]: 2023-12-16 07:41:04 Age [y:d:h:m:s]: 01:131:05:45:41
Block: 914230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354943 RingCT/type: yes/0
Extra: 019072c97bbdf872324f1fdbb5eb912636098e51d2f61e5403306b1c2397ddadc702110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf0205e58da397a2844a2bf20e216ef620d85840f1fbad4c148fcd7087d60df1 0.600000000000 1371516 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": 914240, "vin": [ { "gen": { "height": 914230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf0205e58da397a2844a2bf20e216ef620d85840f1fbad4c148fcd7087d60df1" } } ], "extra": [ 1, 144, 114, 201, 123, 189, 248, 114, 50, 79, 31, 219, 181, 235, 145, 38, 54, 9, 142, 81, 210, 246, 30, 84, 3, 48, 107, 28, 35, 151, 221, 173, 199, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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