Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf81c5edd787e52c4e3c11830946defc2b956bea6108ea4a912140ef08f147a

Tx prefix hash: a3aa67647ccc8f4009d795d2a391ccc2b5867dfd494ab3e4ff9fd990bc274411
Tx public key: f0d3f2342cc502744e74a5a5fb2ff59c3207a2bcf405d68ab3b3ca41550a4010
Timestamp: 1728884305 Timestamp [UCT]: 2024-10-14 05:38:25 Age [y:d:h:m:s]: 00:151:13:26:24
Block: 1131217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108103 RingCT/type: yes/0
Extra: 01f0d3f2342cc502744e74a5a5fb2ff59c3207a2bcf405d68ab3b3ca41550a401002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c572d105ed11a2192906c5c0800c293b61178b70efda38423706a712a0432eab 0.600000000000 1614098 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": 1131227, "vin": [ { "gen": { "height": 1131217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c572d105ed11a2192906c5c0800c293b61178b70efda38423706a712a0432eab" } } ], "extra": [ 1, 240, 211, 242, 52, 44, 197, 2, 116, 78, 116, 165, 165, 251, 47, 245, 156, 50, 7, 162, 188, 244, 5, 214, 138, 179, 179, 202, 65, 85, 10, 64, 16, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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