Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4802b878f2e9d2b32eb24f89c399ef82dc6a49d146bb088fd9a24be925f38c3

Tx prefix hash: e91c158f905d44ef1e35789a2c0ee7617b03f579e04280a56422474dd670ea67
Tx public key: 333db6fc401c6319312b2b0a606c478d5259e58c82f1fbc56100fd95007e892a
Timestamp: 1726295007 Timestamp [UCT]: 2024-09-14 06:23:27 Age [y:d:h:m:s]: 00:162:15:58:58
Block: 1109738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116060 RingCT/type: yes/0
Extra: 01333db6fc401c6319312b2b0a606c478d5259e58c82f1fbc56100fd95007e892a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6e3e649fabcee77976c8bfeac3ecf3b30fca22c4b476299efb427fe52d28dd 0.600000000000 1588101 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": 1109748, "vin": [ { "gen": { "height": 1109738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6e3e649fabcee77976c8bfeac3ecf3b30fca22c4b476299efb427fe52d28dd" } } ], "extra": [ 1, 51, 61, 182, 252, 64, 28, 99, 25, 49, 43, 43, 10, 96, 108, 71, 141, 82, 89, 229, 140, 130, 241, 251, 197, 97, 0, 253, 149, 0, 126, 137, 42, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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