Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e255deb84b9511d2ff7435b65e9093ddb14f52158465134c5b08e54f2606a6f

Tx prefix hash: e1a87d25b3e4c6df37da1dfdeaa5b135dbdad5c0fd7cd326829b7109bb346a3c
Tx public key: 29c1fb7974f753622ba72464eb550b0fd6b0aa96fd32686fcb70ee3f24e34409
Timestamp: 1733895098 Timestamp [UCT]: 2024-12-11 05:31:38 Age [y:d:h:m:s]: 00:103:06:41:00
Block: 1172661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73582 RingCT/type: yes/0
Extra: 0129c1fb7974f753622ba72464eb550b0fd6b0aa96fd32686fcb70ee3f24e34409021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e9c246fe03e0b7bde233f69a8201fec01405a165fe3ba967bb7a3880cec6ca 0.600000000000 1658582 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": 1172671, "vin": [ { "gen": { "height": 1172661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e9c246fe03e0b7bde233f69a8201fec01405a165fe3ba967bb7a3880cec6ca" } } ], "extra": [ 1, 41, 193, 251, 121, 116, 247, 83, 98, 43, 167, 36, 100, 235, 85, 11, 15, 214, 176, 170, 150, 253, 50, 104, 111, 203, 112, 238, 63, 36, 227, 68, 9, 2, 17, 0, 0, 0, 5, 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