Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e5db08aa4b47ea039b5164aaf168c89d3da7b512ba0f22c332b58727d555321

Tx prefix hash: a090fd9ef7230fd2481d23442e35cff5d199cbab5e709c28a931d3b8267f4a9f
Tx public key: 18441c954872b5016f0a4aa9bb18d948e04131dc4ab72b6c2907e55bd2d56c14
Timestamp: 1735780816 Timestamp [UCT]: 2025-01-02 01:20:16 Age [y:d:h:m:s]: 00:348:20:09:43
Block: 1188253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246865 RingCT/type: yes/0
Extra: 0118441c954872b5016f0a4aa9bb18d948e04131dc4ab72b6c2907e55bd2d56c14021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0344aa3ccb734b77df004a5fe26588fb27e3d770a7f80b1601675f75d827604a 0.600000000000 1674754 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": 1188263, "vin": [ { "gen": { "height": 1188253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0344aa3ccb734b77df004a5fe26588fb27e3d770a7f80b1601675f75d827604a" } } ], "extra": [ 1, 24, 68, 28, 149, 72, 114, 181, 1, 111, 10, 74, 169, 187, 24, 217, 72, 224, 65, 49, 220, 74, 183, 43, 108, 41, 7, 229, 91, 210, 213, 108, 20, 2, 17, 0, 0, 0, 1, 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