Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7e6427e26aa71f08ea85f4d047f973e4ffbaf8cce33f872af21fa923abffb7e

Tx prefix hash: ab83111faa914cfd326d251aed2f412e6f7ef00ef4c9a3dac0181943d7894d43
Tx public key: bb0d847c32cef32fa0e539f3297cbda0f45eb7ddfc9403e55dd2e753a964ac42
Timestamp: 1730613171 Timestamp [UCT]: 2024-11-03 05:52:51 Age [y:d:h:m:s]: 00:067:03:22:43
Block: 1145459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48040 RingCT/type: yes/0
Extra: 01bb0d847c32cef32fa0e539f3297cbda0f45eb7ddfc9403e55dd2e753a964ac420211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14d4b9ec9264d694350ddb3de3cde508db74ff694671b3c2025836e1fbc61357 0.600000000000 1629896 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": 1145469, "vin": [ { "gen": { "height": 1145459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14d4b9ec9264d694350ddb3de3cde508db74ff694671b3c2025836e1fbc61357" } } ], "extra": [ 1, 187, 13, 132, 124, 50, 206, 243, 47, 160, 229, 57, 243, 41, 124, 189, 160, 244, 94, 183, 221, 252, 148, 3, 229, 93, 210, 231, 83, 169, 100, 172, 66, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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