Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b03b8b0b59764a0501ccb3d0008d7ef926cc29f222526b623840fc30b46cf4

Tx prefix hash: 319eab815ef8b012eb994b3b02f833e43f3e9e4f101aff0b7038b5f67da39a38
Tx public key: 5222e400847ee79d18e4c7f0bb5c232137556262ece4810e8aac9e957122884d
Timestamp: 1736172950 Timestamp [UCT]: 2025-01-06 14:15:50 Age [y:d:h:m:s]: 00:091:23:06:06
Block: 1191512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65488 RingCT/type: yes/0
Extra: 015222e400847ee79d18e4c7f0bb5c232137556262ece4810e8aac9e957122884d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b7b7e003c2c25870ba6e57ecae1c0bf0b73177a7411d3ed1a3e0bd82eeb4d92 0.600000000000 1678051 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": 1191522, "vin": [ { "gen": { "height": 1191512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b7b7e003c2c25870ba6e57ecae1c0bf0b73177a7411d3ed1a3e0bd82eeb4d92" } } ], "extra": [ 1, 82, 34, 228, 0, 132, 126, 231, 157, 24, 228, 199, 240, 187, 92, 35, 33, 55, 85, 98, 98, 236, 228, 129, 14, 138, 172, 158, 149, 113, 34, 136, 77, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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