Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9738ffab3c42b2794fdc85a160cca74c9f672522d4d92e6648ab0b3ff4c91130

Tx prefix hash: 7158f55d3097e41769d3f189996aedd17fc334c3a0c3bc2089bc3e1c90a1b044
Tx public key: a981fe15e907bb44a8b4db6f48f90f5692fece837d64f40a7b446b4b0010d4d7
Timestamp: 1725621274 Timestamp [UCT]: 2024-09-06 11:14:34 Age [y:d:h:m:s]: 00:284:13:58:31
Block: 1104162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203156 RingCT/type: yes/0
Extra: 01a981fe15e907bb44a8b4db6f48f90f5692fece837d64f40a7b446b4b0010d4d7021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566008819f6d3be010a0c27810d35fe33cefa1d5600e4d0d3ef874ed55f21b7e 0.600000000000 1581241 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": 1104172, "vin": [ { "gen": { "height": 1104162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566008819f6d3be010a0c27810d35fe33cefa1d5600e4d0d3ef874ed55f21b7e" } } ], "extra": [ 1, 169, 129, 254, 21, 233, 7, 187, 68, 168, 180, 219, 111, 72, 249, 15, 86, 146, 254, 206, 131, 125, 100, 244, 10, 123, 68, 107, 75, 0, 16, 212, 215, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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