Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a6a2bd585ef8f136bdf7ec05fa059fce9138f499875986853aad43efe44fea

Tx prefix hash: cdd43c302b8e8c2df7900ae999ad25c1a56af1a811459be549c2b07257ef54ee
Tx public key: e97f9a29a6070fe2ed845eb7b1ab34414dcbec6f7c4e1d7de655de4dfcd732aa
Timestamp: 1738125984 Timestamp [UCT]: 2025-01-29 04:46:24 Age [y:d:h:m:s]: 00:322:15:06:05
Block: 1207419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228365 RingCT/type: yes/0
Extra: 01e97f9a29a6070fe2ed845eb7b1ab34414dcbec6f7c4e1d7de655de4dfcd732aa021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543de0fbd42a7ee4031a57c75eae453674020642a85716be724dd81f552a1364 0.600000000000 1694142 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": 1207429, "vin": [ { "gen": { "height": 1207419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543de0fbd42a7ee4031a57c75eae453674020642a85716be724dd81f552a1364" } } ], "extra": [ 1, 233, 127, 154, 41, 166, 7, 15, 226, 237, 132, 94, 183, 177, 171, 52, 65, 77, 203, 236, 111, 124, 78, 29, 125, 230, 85, 222, 77, 252, 215, 50, 170, 2, 17, 0, 0, 0, 3, 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