Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 630b8d327567f56e528301a83041d8a35e591a77bd1af3c052c93b15a489d7d3

Tx prefix hash: 84c8d6bcb327f68db5d3d72aaf7a1830f61c17b68836765b0e20bd298ed27df7
Tx public key: d1dd15ba8cf8a4a98a19d515532b64428f4b44eca0c3f1473505a049bcbe979f
Timestamp: 1735823785 Timestamp [UCT]: 2025-01-02 13:16:25 Age [y:d:h:m:s]: 00:321:01:49:13
Block: 1188613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226985 RingCT/type: yes/0
Extra: 01d1dd15ba8cf8a4a98a19d515532b64428f4b44eca0c3f1473505a049bcbe979f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 947386edf9e0681350c7eaf9905c1fc4b4e1687248496bfc9b136d5c19b16dff 0.600000000000 1675116 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": 1188623, "vin": [ { "gen": { "height": 1188613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "947386edf9e0681350c7eaf9905c1fc4b4e1687248496bfc9b136d5c19b16dff" } } ], "extra": [ 1, 209, 221, 21, 186, 140, 248, 164, 169, 138, 25, 213, 21, 83, 43, 100, 66, 143, 75, 68, 236, 160, 195, 241, 71, 53, 5, 160, 73, 188, 190, 151, 159, 2, 17, 0, 0, 0, 4, 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