Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e30d311ac321fe18dd56f531e09e3df9caeafbd6a70ad40b1bdb4fe6ab881ff

Tx prefix hash: f1a7ba57d909322ed2b4326030e74d18c81713c28d70ce6259bccfc5afa2a218
Tx public key: 7bcbb207ea50d6dc3dbf6506bf5a02a5016970393f6d3ce32ce5da2de389b413
Timestamp: 1714093421 Timestamp [UCT]: 2024-04-26 01:03:41 Age [y:d:h:m:s]: 00:363:14:12:10
Block: 1008577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259937 RingCT/type: yes/0
Extra: 017bcbb207ea50d6dc3dbf6506bf5a02a5016970393f6d3ce32ce5da2de389b4130211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d599e92c8c051374bca0abc479a618986e193350a08024b0341832ba51168725 0.600000000000 1470049 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": 1008587, "vin": [ { "gen": { "height": 1008577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d599e92c8c051374bca0abc479a618986e193350a08024b0341832ba51168725" } } ], "extra": [ 1, 123, 203, 178, 7, 234, 80, 214, 220, 61, 191, 101, 6, 191, 90, 2, 165, 1, 105, 112, 57, 63, 109, 60, 227, 44, 229, 218, 45, 227, 137, 180, 19, 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