Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d512dd1407817bf4d6cda3b9c2af5ea10e3effa0a9e8b9190952e50798af98

Tx prefix hash: 3f2b80b5a4614caad53e983f18d8af807482596fe23a68540568218a753e5350
Tx public key: ede2ba8409ae7675d674f2894d5530958c1c2e3c114a5ec76221721024cba261
Timestamp: 1674371345 Timestamp [UCT]: 2023-01-22 07:09:05 Age [y:d:h:m:s]: 02:041:23:31:29
Block: 680145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551632 RingCT/type: yes/0
Extra: 01ede2ba8409ae7675d674f2894d5530958c1c2e3c114a5ec76221721024cba261021100000001272bcc39000000000000000000

1 output(s) for total of 3.422923679000 dcy

stealth address amount amount idx
00: ec4b7a5cabba54a762e776d1932d3effa829a34b5f8ff7b772d1c40c3c5f6644 3.422923679000 1122172 of 0

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": 680155, "vin": [ { "gen": { "height": 680145 } } ], "vout": [ { "amount": 3422923679, "target": { "key": "ec4b7a5cabba54a762e776d1932d3effa829a34b5f8ff7b772d1c40c3c5f6644" } } ], "extra": [ 1, 237, 226, 186, 132, 9, 174, 118, 117, 214, 116, 242, 137, 77, 85, 48, 149, 140, 28, 46, 60, 17, 74, 94, 199, 98, 33, 114, 16, 36, 203, 162, 97, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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