Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a9663458326f0d66241bbb1e47f0c6e4f2cadc130ce17bf95318c3451e75ae7

Tx prefix hash: 82e332308918960c432557eb6de950d2d535c76df848b5e522f56a6b3b2797fa
Tx public key: ff97def4c857c49fd5de5c903b4e33c4cfa2bb43e8c750385f79877897be58ac
Timestamp: 1700484386 Timestamp [UCT]: 2023-11-20 12:46:26 Age [y:d:h:m:s]: 01:145:17:28:39
Block: 895761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365346 RingCT/type: yes/0
Extra: 01ff97def4c857c49fd5de5c903b4e33c4cfa2bb43e8c750385f79877897be58ac02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.660650775000 dcy

stealth address amount amount idx
00: adba95001d7929545cdf689708d099ec2f9b6e245af7d1d52e652fc16449a517 0.660650775000 1352008 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": 895771, "vin": [ { "gen": { "height": 895761 } } ], "vout": [ { "amount": 660650775, "target": { "key": "adba95001d7929545cdf689708d099ec2f9b6e245af7d1d52e652fc16449a517" } } ], "extra": [ 1, 255, 151, 222, 244, 200, 87, 196, 159, 213, 222, 92, 144, 59, 78, 51, 196, 207, 162, 187, 67, 232, 199, 80, 56, 95, 121, 135, 120, 151, 190, 88, 172, 2, 17, 0, 0, 0, 1, 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