Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c5deb702978a28d6f4d3751893c04c45ee7926b253cf6377b057cc5dc6ad92

Tx prefix hash: 1cb746c9a4c20dfc0064323e250a33d08586cd4a7901fa861d78c9420314413c
Tx public key: 437e3999e1616544ef5dc94ff1f4fb235bdf5cd8783aa9bd079ab6d57c1b511a
Timestamp: 1737140179 Timestamp [UCT]: 2025-01-17 18:56:19 Age [y:d:h:m:s]: 00:058:04:40:40
Block: 1199504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41380 RingCT/type: yes/0
Extra: 01437e3999e1616544ef5dc94ff1f4fb235bdf5cd8783aa9bd079ab6d57c1b511a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 526cd4729fdd58d1c8fe834962e937fc94ab04cb0c04f3c1966410b884897ec6 0.600000000000 1686135 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": 1199514, "vin": [ { "gen": { "height": 1199504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "526cd4729fdd58d1c8fe834962e937fc94ab04cb0c04f3c1966410b884897ec6" } } ], "extra": [ 1, 67, 126, 57, 153, 225, 97, 101, 68, 239, 93, 201, 79, 241, 244, 251, 35, 91, 223, 92, 216, 120, 58, 169, 189, 7, 154, 182, 213, 124, 27, 81, 26, 2, 17, 0, 0, 0, 3, 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