Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47beeafad85bc4d75b51194acf74844207bf5a7571d8ce566ab3316aae21df5

Tx prefix hash: 680f33cafb2212dcdd7e0cd351f5d7bf53b782f0f0255391838fd3fae8e78282
Tx public key: d30de97ea4f1606109aa67486ae8b34969354e722ee5e22005bbd93be0ecff6c
Timestamp: 1724130476 Timestamp [UCT]: 2024-08-20 05:07:56 Age [y:d:h:m:s]: 00:305:08:01:14
Block: 1091806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217962 RingCT/type: yes/0
Extra: 01d30de97ea4f1606109aa67486ae8b34969354e722ee5e22005bbd93be0ecff6c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b775059159147a89cdb2d4bab97f8d7b5db23238e84ad6c8d0b4d08b20acff1 0.600000000000 1566441 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": 1091816, "vin": [ { "gen": { "height": 1091806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b775059159147a89cdb2d4bab97f8d7b5db23238e84ad6c8d0b4d08b20acff1" } } ], "extra": [ 1, 211, 13, 233, 126, 164, 241, 96, 97, 9, 170, 103, 72, 106, 232, 179, 73, 105, 53, 78, 114, 46, 229, 226, 32, 5, 187, 217, 59, 224, 236, 255, 108, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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