Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7451845e1153b401b6d8a3badcb30e389e4f9e6db4d9c72a6bb5fd5a0cef7b

Tx prefix hash: 1022b9f11959345ee24466884bd33f8eac77c59edc31d95f330381a040058f9e
Tx public key: a04cc11468fa6a3078aae2bd825c187cc9ba89f8f6e7bc1cf3b4bd71e9cb6e8e
Timestamp: 1719590158 Timestamp [UCT]: 2024-06-28 15:55:58 Age [y:d:h:m:s]: 00:240:06:46:50
Block: 1054146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171659 RingCT/type: yes/0
Extra: 01a04cc11468fa6a3078aae2bd825c187cc9ba89f8f6e7bc1cf3b4bd71e9cb6e8e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2357da77d890754dbee5f5f99c1140cbd66722ba3d857e5ca5d4996a2d95b35 0.600000000000 1524505 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": 1054156, "vin": [ { "gen": { "height": 1054146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2357da77d890754dbee5f5f99c1140cbd66722ba3d857e5ca5d4996a2d95b35" } } ], "extra": [ 1, 160, 76, 193, 20, 104, 250, 106, 48, 120, 170, 226, 189, 130, 92, 24, 124, 201, 186, 137, 248, 246, 231, 188, 28, 243, 180, 189, 113, 233, 203, 110, 142, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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