Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7fc23cf60b5dc6bec507f9ea4498ead2e19dada12a7fb0a7675191b18c09df

Tx prefix hash: 286f911fcbfa89148476b522932045b17c3e4480d037c3c3bd6a59f4af39f9ca
Tx public key: f3320af330470ef5985c5df869052be570b84e6c946a864e63b5c6ad9e3147e0
Timestamp: 1716464156 Timestamp [UCT]: 2024-05-23 11:35:56 Age [y:d:h:m:s]: 00:357:02:07:15
Block: 1028250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255250 RingCT/type: yes/0
Extra: 01f3320af330470ef5985c5df869052be570b84e6c946a864e63b5c6ad9e3147e00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdde69f58d41ec3d8a9380ce440a3da612a8fa6937c7caeb9bb4ddb78afdeae0 0.600000000000 1496215 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": 1028260, "vin": [ { "gen": { "height": 1028250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdde69f58d41ec3d8a9380ce440a3da612a8fa6937c7caeb9bb4ddb78afdeae0" } } ], "extra": [ 1, 243, 50, 10, 243, 48, 71, 14, 245, 152, 92, 93, 248, 105, 5, 43, 229, 112, 184, 78, 108, 148, 106, 134, 78, 99, 181, 198, 173, 158, 49, 71, 224, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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