Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9435c114ca0a6306931b7b1bfd22935b84696bc9a83fe811b26d1f94025a1181

Tx prefix hash: 968d9779527d3e6fb631ce6550f4c696931f3209d98dcf47e37d52acf5850688
Tx public key: 05d72cc2c6c6b788cc256764c0f8e79afeac69827847376c96a5cf0500e17bcf
Timestamp: 1716166293 Timestamp [UCT]: 2024-05-20 00:51:33 Age [y:d:h:m:s]: 00:313:05:19:19
Block: 1025777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223866 RingCT/type: yes/0
Extra: 0105d72cc2c6c6b788cc256764c0f8e79afeac69827847376c96a5cf0500e17bcf0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1de9fd613a5d189c1d56c3ec55c05151364b692a8e2d0f3cae348d7bac71c908 0.600000000000 1492494 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": 1025787, "vin": [ { "gen": { "height": 1025777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1de9fd613a5d189c1d56c3ec55c05151364b692a8e2d0f3cae348d7bac71c908" } } ], "extra": [ 1, 5, 215, 44, 194, 198, 198, 183, 136, 204, 37, 103, 100, 192, 248, 231, 154, 254, 172, 105, 130, 120, 71, 55, 108, 150, 165, 207, 5, 0, 225, 123, 207, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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