Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2de6dd6f241ac0d32e3e8fa36f806c836f41d8a90cf050730a307c2518d7ac1

Tx prefix hash: f500100edf9db5d3d1a394b7961ac306572a61fee14923c220a6f33807cb94dd
Tx public key: 20d06aaa50c3cf1da2bd3cfc53690ef24fad9196a37e3a9c9e80ff2050e9f05d
Timestamp: 1736738706 Timestamp [UCT]: 2025-01-13 03:25:06 Age [y:d:h:m:s]: 00:068:08:27:08
Block: 1196184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48630 RingCT/type: yes/0
Extra: 0120d06aaa50c3cf1da2bd3cfc53690ef24fad9196a37e3a9c9e80ff2050e9f05d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ab6495eb5d3ddad34013b3a138b97d1c6bdb9149170576a08c911bf0a97a8f 0.600000000000 1682781 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": 1196194, "vin": [ { "gen": { "height": 1196184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ab6495eb5d3ddad34013b3a138b97d1c6bdb9149170576a08c911bf0a97a8f" } } ], "extra": [ 1, 32, 208, 106, 170, 80, 195, 207, 29, 162, 189, 60, 252, 83, 105, 14, 242, 79, 173, 145, 150, 163, 126, 58, 156, 158, 128, 255, 32, 80, 233, 240, 93, 2, 17, 0, 0, 0, 2, 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