Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c95622aae13ba68473a40d0637dd07b4bfce5f85de9dca68e95ba0f0e4ed03

Tx prefix hash: 4cd9a2e510f1e88e623b0e964cc765c77307ca98e1a28afc8eae05e28e505bed
Tx public key: a6ff40e735cd89da1ffa4ae1e3d14b2ee71894a315c980eccc40cb15fb0140a1
Timestamp: 1737871478 Timestamp [UCT]: 2025-01-26 06:04:38 Age [y:d:h:m:s]: 00:330:14:36:57
Block: 1205519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233877 RingCT/type: yes/0
Extra: 01a6ff40e735cd89da1ffa4ae1e3d14b2ee71894a315c980eccc40cb15fb0140a1021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b747219fa4ae61c80bf504e741c88af242702485724803c47a1daa161725f61d 0.600000000000 1692216 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": 1205529, "vin": [ { "gen": { "height": 1205519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b747219fa4ae61c80bf504e741c88af242702485724803c47a1daa161725f61d" } } ], "extra": [ 1, 166, 255, 64, 231, 53, 205, 137, 218, 31, 250, 74, 225, 227, 209, 75, 46, 231, 24, 148, 163, 21, 201, 128, 236, 204, 64, 203, 21, 251, 1, 64, 161, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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