Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 707e121c983efdd4be4f7dea302a8573569baf2aa21c43ae1e9b8b585c865cda

Tx prefix hash: 84fd2825dbef1ba245b769d4c45e3c8768fe14da2dc3156dba385c65a62bd529
Tx public key: d5effb185934bfaf76a927b8a59b694b9050877d7713c413d2ee7f49247710d3
Timestamp: 1729081804 Timestamp [UCT]: 2024-10-16 12:30:04 Age [y:d:h:m:s]: 00:149:03:07:13
Block: 1132866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106348 RingCT/type: yes/0
Extra: 01d5effb185934bfaf76a927b8a59b694b9050877d7713c413d2ee7f49247710d30211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d545db3f9bcf558c16ee07c1a882a156c8b8d1378e6a3797089f97a7a8205601 0.600000000000 1615883 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": 1132876, "vin": [ { "gen": { "height": 1132866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d545db3f9bcf558c16ee07c1a882a156c8b8d1378e6a3797089f97a7a8205601" } } ], "extra": [ 1, 213, 239, 251, 24, 89, 52, 191, 175, 118, 169, 39, 184, 165, 155, 105, 75, 144, 80, 135, 125, 119, 19, 196, 19, 210, 238, 127, 73, 36, 119, 16, 211, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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