Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a307d38db8ac64f72f1a36755a8d0f7601e3d28e48ce2b7d1c2fee8e21f78320

Tx prefix hash: f384a5435fe994d4f3fb104a6deb6da595c5ad35f93ae848c68db4c3dd26fe07
Tx public key: a9e002a0ce1d3cb503cfca9fe47e038b2e8f6a32cf54fbed3abab959ee8259a0
Timestamp: 1714358733 Timestamp [UCT]: 2024-04-29 02:45:33 Age [y:d:h:m:s]: 01:001:10:23:58
Block: 1010783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261956 RingCT/type: yes/0
Extra: 01a9e002a0ce1d3cb503cfca9fe47e038b2e8f6a32cf54fbed3abab959ee8259a002110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 688cbd9264307770cf0a69ee138c8d17d7f04c6b6a644317b314cdd0e33e41cf 0.600000000000 1472831 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": 1010793, "vin": [ { "gen": { "height": 1010783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "688cbd9264307770cf0a69ee138c8d17d7f04c6b6a644317b314cdd0e33e41cf" } } ], "extra": [ 1, 169, 224, 2, 160, 206, 29, 60, 181, 3, 207, 202, 159, 228, 126, 3, 139, 46, 143, 106, 50, 207, 84, 251, 237, 58, 186, 185, 89, 238, 130, 89, 160, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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