Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8637c0adc38b619accaf07b3a472eb097ddf860635a635372a429fa00f7fa6

Tx prefix hash: feba87e866b863a4e5ae1bd91152837c0783c5641ef5a7cb5beed5458119904a
Tx public key: 3249d558edbca15a32c3bea5ee40f82f2c45e7da9d33f8c098df33ad8a77d985
Timestamp: 1736504215 Timestamp [UCT]: 2025-01-10 10:16:55 Age [y:d:h:m:s]: 00:347:02:28:34
Block: 1194237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245625 RingCT/type: yes/0
Extra: 013249d558edbca15a32c3bea5ee40f82f2c45e7da9d33f8c098df33ad8a77d9850211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bba298e52007731fce2b51d74eb9d6938273e3432c6b59ef2a4f72f6baf3061 0.600000000000 1680804 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": 1194247, "vin": [ { "gen": { "height": 1194237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bba298e52007731fce2b51d74eb9d6938273e3432c6b59ef2a4f72f6baf3061" } } ], "extra": [ 1, 50, 73, 213, 88, 237, 188, 161, 90, 50, 195, 190, 165, 238, 64, 248, 47, 44, 69, 231, 218, 157, 51, 248, 192, 152, 223, 51, 173, 138, 119, 217, 133, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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