Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f97d22d9d1a495536cc77fdaaef8ed94c5cd8e61774bed54092a832a7f8f864

Tx prefix hash: cb3a23987dc1616d568d592a34ae7a5382646a75eed91b1d02f7cc625ce9428d
Tx public key: 1bdf9b9977540b40862acc94891d63902222553fa3eed8a26ec061604bb625b9
Timestamp: 1696699060 Timestamp [UCT]: 2023-10-07 17:17:40 Age [y:d:h:m:s]: 01:219:09:08:01
Block: 864579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417860 RingCT/type: yes/0
Extra: 011bdf9b9977540b40862acc94891d63902222553fa3eed8a26ec061604bb625b902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.838090474000 dcy

stealth address amount amount idx
00: 8cf14b0aaf7cc8a6f89813e89d87f2c7e3f57468df4b93267267fbb68f9dd72e 0.838090474000 1319099 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": 864589, "vin": [ { "gen": { "height": 864579 } } ], "vout": [ { "amount": 838090474, "target": { "key": "8cf14b0aaf7cc8a6f89813e89d87f2c7e3f57468df4b93267267fbb68f9dd72e" } } ], "extra": [ 1, 27, 223, 155, 153, 119, 84, 11, 64, 134, 42, 204, 148, 137, 29, 99, 144, 34, 34, 85, 63, 163, 238, 216, 162, 110, 192, 97, 96, 75, 182, 37, 185, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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