Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11592d3e0aacf0bde12bd417855c5504ce066e39e4837c705d85d04342e9f92c

Tx prefix hash: dd52098dfb4e9152fbaf5e2745bca5e1b9972d4661862a74b33c18b0fec33d46
Tx public key: f62cb055333fc71b425a2e2fb985d4b0a1e9bc3fb1c45fbef9d01891081a4c63
Timestamp: 1713482970 Timestamp [UCT]: 2024-04-18 23:29:30 Age [y:d:h:m:s]: 00:309:15:30:08
Block: 1003518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221328 RingCT/type: yes/0
Extra: 01f62cb055333fc71b425a2e2fb985d4b0a1e9bc3fb1c45fbef9d01891081a4c63021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c730d3f543c978162294bce566de38b7bfb9ec65aa8eea127a772552d70e51b8 0.600000000000 1464060 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": 1003528, "vin": [ { "gen": { "height": 1003518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c730d3f543c978162294bce566de38b7bfb9ec65aa8eea127a772552d70e51b8" } } ], "extra": [ 1, 246, 44, 176, 85, 51, 63, 199, 27, 66, 90, 46, 47, 185, 133, 212, 176, 161, 233, 188, 63, 177, 196, 95, 190, 249, 208, 24, 145, 8, 26, 76, 99, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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