Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ecccd9858ac6e7a6ca4d2384f32e5de8038165e7da4395ffceb82807806c164

Tx prefix hash: 6e1df81e418a07f114e1c05b673e856666dff153d1f6ba1ff8672b547066e04f
Tx public key: 2782194e18825547e972f0b0da3d16fbe8dfabb41510f426cfe97fdbafa5bef7
Timestamp: 1698422412 Timestamp [UCT]: 2023-10-27 16:00:12 Age [y:d:h:m:s]: 01:119:00:22:02
Block: 878885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346007 RingCT/type: yes/0
Extra: 012782194e18825547e972f0b0da3d16fbe8dfabb41510f426cfe97fdbafa5bef70211000000024b8f5122000000000000000000

1 output(s) for total of 0.751431102000 dcy

stealth address amount amount idx
00: 745c96e44bcec5b8e081ca50e0b7802fde162cf34fbd1de7656e0f8c09ba18ac 0.751431102000 1334377 of 0

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": 878895, "vin": [ { "gen": { "height": 878885 } } ], "vout": [ { "amount": 751431102, "target": { "key": "745c96e44bcec5b8e081ca50e0b7802fde162cf34fbd1de7656e0f8c09ba18ac" } } ], "extra": [ 1, 39, 130, 25, 78, 24, 130, 85, 71, 233, 114, 240, 176, 218, 61, 22, 251, 232, 223, 171, 180, 21, 16, 244, 38, 207, 233, 127, 219, 175, 165, 190, 247, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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