Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07732eb1d3d9d919033bacfe5e736f52cc57ca819011f6d3363dbda3a4d86339

Tx prefix hash: dca75265718f6ba904601709d1370e6cf9832078bca4aeb7c4fa8123ac318d4b
Tx public key: 03a9e47564e8063da34a106316d0aa34557d243ccdc11dcc925fd5c6413c6d8b
Timestamp: 1724505690 Timestamp [UCT]: 2024-08-24 13:21:30 Age [y:d:h:m:s]: 00:254:22:43:30
Block: 1094928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182073 RingCT/type: yes/0
Extra: 0103a9e47564e8063da34a106316d0aa34557d243ccdc11dcc925fd5c6413c6d8b021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1635936403aa7857473b6d12c93b9d27477ca6c1855065aa9dbae0d5bf624c81 0.600000000000 1570049 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": 1094938, "vin": [ { "gen": { "height": 1094928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1635936403aa7857473b6d12c93b9d27477ca6c1855065aa9dbae0d5bf624c81" } } ], "extra": [ 1, 3, 169, 228, 117, 100, 232, 6, 61, 163, 74, 16, 99, 22, 208, 170, 52, 85, 125, 36, 60, 205, 193, 29, 204, 146, 95, 213, 198, 65, 60, 109, 139, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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