Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d3f6714ecb1c9ebfdd0ab532c4337f4201afafaad038ebb4813f18a1f9adf0

Tx prefix hash: 4a7a204cba0daf50730e800476e9a05cca3117df310f448b2a46ae30d9315af7
Tx public key: f9f6f97b18ba744ce04f281f947e71f8f1e69777b7d6f60e6f9f73edcdf1f3b0
Timestamp: 1633113020 Timestamp [UCT]: 2021-10-01 18:30:20 Age [y:d:h:m:s]: 04:008:13:08:03
Block: 344649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1041363 RingCT/type: yes/0
Extra: 01f9f6f97b18ba744ce04f281f947e71f8f1e69777b7d6f60e6f9f73edcdf1f3b0021100000001f29d7abf000000000000000000

1 output(s) for total of 44.264206674000 dcy

stealth address amount amount idx
00: ffe3e3eaf5594967c011c43aecc5bb05a04a259dffb40222b1cf04ae49c66a35 44.264206674000 707105 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": 344659, "vin": [ { "gen": { "height": 344649 } } ], "vout": [ { "amount": 44264206674, "target": { "key": "ffe3e3eaf5594967c011c43aecc5bb05a04a259dffb40222b1cf04ae49c66a35" } } ], "extra": [ 1, 249, 246, 249, 123, 24, 186, 116, 76, 224, 79, 40, 31, 148, 126, 113, 248, 241, 230, 151, 119, 183, 214, 246, 14, 111, 159, 115, 237, 205, 241, 243, 176, 2, 17, 0, 0, 0, 1, 242, 157, 122, 191, 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