Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d153c9966e62d0ac59640d773b8749e2d4e4ff415892e7233713056c446b28b

Tx prefix hash: 558acb8d593e6ab957ff1ed5a4be8b94f03494286007b62d528a7382d3d0f14c
Tx public key: 86a97664a3e4d032f09ef96dba309ee3f47bd43a15d4d5b07556dcd0c2426555
Timestamp: 1720867598 Timestamp [UCT]: 2024-07-13 10:46:38 Age [y:d:h:m:s]: 00:198:06:14:28
Block: 1064755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141614 RingCT/type: yes/0
Extra: 0186a97664a3e4d032f09ef96dba309ee3f47bd43a15d4d5b07556dcd0c242655502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7fc16eabc6ae8de7243fab02b29dc1597da096da7ddff7ffb143f8fc6aef070 0.600000000000 1535294 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": 1064765, "vin": [ { "gen": { "height": 1064755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7fc16eabc6ae8de7243fab02b29dc1597da096da7ddff7ffb143f8fc6aef070" } } ], "extra": [ 1, 134, 169, 118, 100, 163, 228, 208, 50, 240, 158, 249, 109, 186, 48, 158, 227, 244, 123, 212, 58, 21, 212, 213, 176, 117, 86, 220, 208, 194, 66, 101, 85, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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