Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7af92fbc01d29a8bc80ef91e0f6dd924d34b1ccb4abf2bbc5a2e309fb914cd2

Tx prefix hash: 317fa4397af73d4103c6250d834b1b774448316234d12be68f42c0c295c60891
Tx public key: d4327ef27a4d4d88e502522593cbb66da335c4688d4021c74308681c3c77a2ee
Timestamp: 1707942507 Timestamp [UCT]: 2024-02-14 20:28:27 Age [y:d:h:m:s]: 01:087:13:35:45
Block: 957580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323655 RingCT/type: yes/0
Extra: 01d4327ef27a4d4d88e502522593cbb66da335c4688d4021c74308681c3c77a2ee02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25bccada8ae8c6380a16a73e03b063f48e0e05f91dd852f26a8ce6dcf013633d 0.600000000000 1416898 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": 957590, "vin": [ { "gen": { "height": 957580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25bccada8ae8c6380a16a73e03b063f48e0e05f91dd852f26a8ce6dcf013633d" } } ], "extra": [ 1, 212, 50, 126, 242, 122, 77, 77, 136, 229, 2, 82, 37, 147, 203, 182, 109, 163, 53, 196, 104, 141, 64, 33, 199, 67, 8, 104, 28, 60, 119, 162, 238, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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