Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8098b83b3c63c5e5c8304fa976db26585a8154118c184b1aee1f2571271552b2

Tx prefix hash: f91af5593e04cfc2ec547599f02d2832c93b3c754d166528e23f27d571c8950b
Tx public key: 6d7c677282193b379e148317eb6ee820e8d015c4dd1aedf200a98e77c1c3306d
Timestamp: 1705515790 Timestamp [UCT]: 2024-01-17 18:23:10 Age [y:d:h:m:s]: 01:006:21:00:49
Block: 937451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266206 RingCT/type: yes/0
Extra: 016d7c677282193b379e148317eb6ee820e8d015c4dd1aedf200a98e77c1c3306d02110000000182025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5840f78fa3a3469a129cdb69ca0e232c90e902620745a8ae853c59f24df84ac 0.600000000000 1395505 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": 937461, "vin": [ { "gen": { "height": 937451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5840f78fa3a3469a129cdb69ca0e232c90e902620745a8ae853c59f24df84ac" } } ], "extra": [ 1, 109, 124, 103, 114, 130, 25, 59, 55, 158, 20, 131, 23, 235, 110, 232, 32, 232, 208, 21, 196, 221, 26, 237, 242, 0, 169, 142, 119, 193, 195, 48, 109, 2, 17, 0, 0, 0, 1, 130, 2, 82, 104, 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