Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80cd3f1d3eb78027628d1670e384b445b3290ef116b9a153011768403ba39e7f

Tx prefix hash: ff6e613e6500db71198d3e6b138a926bf450b4a0b472ed24be48bf5e7726ec0b
Tx public key: 322cea8731e66d56b6230f1495499d1ffefdcc2c3439b0ba8acb34b8e2fe698c
Timestamp: 1701979346 Timestamp [UCT]: 2023-12-07 20:02:26 Age [y:d:h:m:s]: 01:101:17:34:08
Block: 908154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333865 RingCT/type: yes/0
Extra: 01322cea8731e66d56b6230f1495499d1ffefdcc2c3439b0ba8acb34b8e2fe698c021100000003faf35c9c000000000000000000

1 output(s) for total of 0.601047475000 dcy

stealth address amount amount idx
00: b06542d0594f16a96e7a503010e175a26611d3e4819eee87c984c79ad6d559a7 0.601047475000 1365179 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": 908164, "vin": [ { "gen": { "height": 908154 } } ], "vout": [ { "amount": 601047475, "target": { "key": "b06542d0594f16a96e7a503010e175a26611d3e4819eee87c984c79ad6d559a7" } } ], "extra": [ 1, 50, 44, 234, 135, 49, 230, 109, 86, 182, 35, 15, 20, 149, 73, 157, 31, 254, 253, 204, 44, 52, 57, 176, 186, 138, 203, 52, 184, 226, 254, 105, 140, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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