Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9e3111508636f4d283a107313d726c487710a93d1d430e0706fed3cbc93065

Tx prefix hash: 95692ead7db0709d0670b14ff349e7666e726e47537cc73a1234358f7bd5a901
Tx public key: 67272cd1d6150e54b08d293084a23795b0c6ebd84deda3fdcb29c75b6981277c
Timestamp: 1708788799 Timestamp [UCT]: 2024-02-24 15:33:19 Age [y:d:h:m:s]: 01:053:17:36:31
Block: 964618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299422 RingCT/type: yes/0
Extra: 0167272cd1d6150e54b08d293084a23795b0c6ebd84deda3fdcb29c75b6981277c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac9f1024fcf9c0e7e2b7caaec6a12e425bca75b4c5a5618a6f021c371898fea0 0.600000000000 1424359 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": 964628, "vin": [ { "gen": { "height": 964618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac9f1024fcf9c0e7e2b7caaec6a12e425bca75b4c5a5618a6f021c371898fea0" } } ], "extra": [ 1, 103, 39, 44, 209, 214, 21, 14, 84, 176, 141, 41, 48, 132, 162, 55, 149, 176, 198, 235, 216, 77, 237, 163, 253, 203, 41, 199, 91, 105, 129, 39, 124, 2, 17, 0, 0, 0, 3, 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