Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6907c2250b9013a3fa83e300abc4ba78d2568a3432a83abe1369a7a1c9fce8

Tx prefix hash: bbb146a68e5859ce04c9afc71034a03aef59cb3c8317c4186d5c291c4322be43
Tx public key: b9c0e9748e93f4f78888b9748791d1e9755c3297fd4246fd8fe4ffdf98e33f1b
Timestamp: 1694302043 Timestamp [UCT]: 2023-09-09 23:27:23 Age [y:d:h:m:s]: 01:172:10:21:41
Block: 844687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384308 RingCT/type: yes/0
Extra: 01b9c0e9748e93f4f78888b9748791d1e9755c3297fd4246fd8fe4ffdf98e33f1b0211000000184b8f5122000000000000000000

1 output(s) for total of 0.975441856000 dcy

stealth address amount amount idx
00: e6263747b17ba4e3faac436d8b1fc5b4836a4eb55ed37563d83db663d4ff8feb 0.975441856000 1298011 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": 844697, "vin": [ { "gen": { "height": 844687 } } ], "vout": [ { "amount": 975441856, "target": { "key": "e6263747b17ba4e3faac436d8b1fc5b4836a4eb55ed37563d83db663d4ff8feb" } } ], "extra": [ 1, 185, 192, 233, 116, 142, 147, 244, 247, 136, 136, 185, 116, 135, 145, 209, 233, 117, 92, 50, 151, 253, 66, 70, 253, 143, 228, 255, 223, 152, 227, 63, 27, 2, 17, 0, 0, 0, 24, 75, 143, 81, 34, 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