Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf6847ba7fb2860fbebbf27ae86b3c28e1c5ade022294adf95f0cb0e6fa9fb1

Tx prefix hash: 709a25130e62467368f4dce367fbcec42c9471b4ee32c891f6f3015d3560614d
Tx public key: 4739c983563ee124200a93a799f1a686ac2f7f7380fb3478d15a4e6389fbecbb
Timestamp: 1702755929 Timestamp [UCT]: 2023-12-16 19:45:29 Age [y:d:h:m:s]: 01:329:20:23:31
Block: 914595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494601 RingCT/type: yes/0
Extra: 014739c983563ee124200a93a799f1a686ac2f7f7380fb3478d15a4e6389fbecbb021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fdf464a6621f017fa629e9960b55a762a8b4b82fe96a5ba3d9f00a65f1545b2 0.600000000000 1371941 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": 914605, "vin": [ { "gen": { "height": 914595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fdf464a6621f017fa629e9960b55a762a8b4b82fe96a5ba3d9f00a65f1545b2" } } ], "extra": [ 1, 71, 57, 201, 131, 86, 62, 225, 36, 32, 10, 147, 167, 153, 241, 166, 134, 172, 47, 127, 115, 128, 251, 52, 120, 209, 90, 78, 99, 137, 251, 236, 187, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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