Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b378627a8d8eaf9c014a8a1d9f62d4a50b0ab5f31dfbf515b7c033d136c293

Tx prefix hash: 19c9284bfefbfe8569ede28a2e1538b0381ba7564d13cf776f3837257654a8b1
Tx public key: 377effa6047d2af0663cbfd618865ab75649f329f8ecc7891bcdb3d1c20274a7
Timestamp: 1722178398 Timestamp [UCT]: 2024-07-28 14:53:18 Age [y:d:h:m:s]: 00:269:15:03:22
Block: 1075614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192620 RingCT/type: yes/0
Extra: 01377effa6047d2af0663cbfd618865ab75649f329f8ecc7891bcdb3d1c20274a702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc31bbdfc6f938b3ae4bc28b96d754116e0bf7fb3fc3fae0bd514a627c084762 0.600000000000 1548143 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": 1075624, "vin": [ { "gen": { "height": 1075614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc31bbdfc6f938b3ae4bc28b96d754116e0bf7fb3fc3fae0bd514a627c084762" } } ], "extra": [ 1, 55, 126, 255, 166, 4, 125, 42, 240, 102, 60, 191, 214, 24, 134, 90, 183, 86, 73, 243, 41, 248, 236, 199, 137, 27, 205, 179, 209, 194, 2, 116, 167, 2, 17, 0, 0, 0, 7, 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