Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c537de2a9151ffac6a0d47d185efd78e2f0a69fa06448d2044ec4258383fe3ef

Tx prefix hash: 7a2de15e81091e78f1d2baa48cfd1dd42b9fb1340100a632325602087da568f3
Tx public key: 06d1a69414500db3ead772a098c3266e8ab59fe5b9c23b6b72d67f9bd4874834
Timestamp: 1724507002 Timestamp [UCT]: 2024-08-24 13:43:22 Age [y:d:h:m:s]: 00:297:11:14:34
Block: 1094944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212360 RingCT/type: yes/0
Extra: 0106d1a69414500db3ead772a098c3266e8ab59fe5b9c23b6b72d67f9bd4874834021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2ec8ed8d9f28d8816d3bc6740a8a1ec5ef017072f3d632fb455fb50da157a0 0.600000000000 1570065 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": 1094954, "vin": [ { "gen": { "height": 1094944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2ec8ed8d9f28d8816d3bc6740a8a1ec5ef017072f3d632fb455fb50da157a0" } } ], "extra": [ 1, 6, 209, 166, 148, 20, 80, 13, 179, 234, 215, 114, 160, 152, 195, 38, 110, 138, 181, 159, 229, 185, 194, 59, 107, 114, 214, 127, 155, 212, 135, 72, 52, 2, 17, 0, 0, 0, 1, 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