Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da62867d135ff83f47f35aec33f3b0c540ba95783f826b386eff2f1d5d35f793

Tx prefix hash: cf354d7b5c88f7dd4a02e022b805fb2dd524ea9e6363c66709de6381cd90323c
Tx public key: 27b0e9e7079a4756504e6d6666ee77c895b07ba71d5f41a73fca1e508780ee75
Timestamp: 1737991141 Timestamp [UCT]: 2025-01-27 15:19:01 Age [y:d:h:m:s]: 00:002:15:41:24
Block: 1206316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1875 RingCT/type: yes/0
Extra: 0127b0e9e7079a4756504e6d6666ee77c895b07ba71d5f41a73fca1e508780ee7502110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b968cd3cb78950a83af6f265a35e70363ec56e3b15b3039f2cc8fb8c2e676bd 0.600000000000 1693019 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": 1206326, "vin": [ { "gen": { "height": 1206316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b968cd3cb78950a83af6f265a35e70363ec56e3b15b3039f2cc8fb8c2e676bd" } } ], "extra": [ 1, 39, 176, 233, 231, 7, 154, 71, 86, 80, 78, 109, 102, 102, 238, 119, 200, 149, 176, 123, 167, 29, 95, 65, 167, 63, 202, 30, 80, 135, 128, 238, 117, 2, 17, 0, 0, 0, 15, 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