Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df896f6983e428b8ee92e7ed9c51feb7d9df345282f8849fb016d1682c0de304

Tx prefix hash: d307cdff921e0a0f82f06e8e2cc0978d37ec8b8e8e832d141847a49fd748ad08
Tx public key: f0510e00b80962966759ddf8e0bdf44508b10aa54fd6c0aeee4be8e51379f3d6
Timestamp: 1700905940 Timestamp [UCT]: 2023-11-25 09:52:20 Age [y:d:h:m:s]: 01:096:13:34:50
Block: 899257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330148 RingCT/type: yes/0
Extra: 01f0510e00b80962966759ddf8e0bdf44508b10aa54fd6c0aeee4be8e51379f3d6021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.643262515000 dcy

stealth address amount amount idx
00: 4ffd4d48c64cdd6f7714fc62c341bc426c45936f1fb6f686ee9035b2ee4c63f2 0.643262515000 1355704 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": 899267, "vin": [ { "gen": { "height": 899257 } } ], "vout": [ { "amount": 643262515, "target": { "key": "4ffd4d48c64cdd6f7714fc62c341bc426c45936f1fb6f686ee9035b2ee4c63f2" } } ], "extra": [ 1, 240, 81, 14, 0, 184, 9, 98, 150, 103, 89, 221, 248, 224, 189, 244, 69, 8, 177, 10, 165, 79, 214, 192, 174, 238, 75, 232, 229, 19, 121, 243, 214, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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