Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e2ae17615b80a281403bf28a0cbb26be5a96fce5717ba531139f8c85350fb29

Tx prefix hash: 30013982b944c3ec9deefa1c9952e388e41f070d6ffe20657de8102ab0254c6c
Tx public key: f184681ffca9d1333fb28270b2f87aac8bfca0c36a515da3b88a680943f04f6f
Timestamp: 1718329006 Timestamp [UCT]: 2024-06-14 01:36:46 Age [y:d:h:m:s]: 00:307:03:51:59
Block: 1043709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219494 RingCT/type: yes/0
Extra: 01f184681ffca9d1333fb28270b2f87aac8bfca0c36a515da3b88a680943f04f6f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ecc1edd3248e41c80edb00cf380bf8ab63405a616fa1b0b1c9b2d3d89c70a9 0.600000000000 1512868 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": 1043719, "vin": [ { "gen": { "height": 1043709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ecc1edd3248e41c80edb00cf380bf8ab63405a616fa1b0b1c9b2d3d89c70a9" } } ], "extra": [ 1, 241, 132, 104, 31, 252, 169, 209, 51, 63, 178, 130, 112, 178, 248, 122, 172, 139, 252, 160, 195, 106, 81, 93, 163, 184, 138, 104, 9, 67, 240, 79, 111, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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