Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71adca6cb59ca03c18f3caaf5882ca26f0961f4ef8abd5353a1e0a96f33a7cee

Tx prefix hash: 933c9dd2e9dd32d97e3a14ec66e8ea730ac254bbebe20222c76f2edbcc14d7d6
Tx public key: 9ca7968deaa561a5c9e3cb04a904625e3ca10a95efc9c19a4d81a7e4219b3cc6
Timestamp: 1631643365 Timestamp [UCT]: 2021-09-14 18:16:05 Age [y:d:h:m:s]: 03:176:18:32:33
Block: 333778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 901772 RingCT/type: yes/0
Extra: 019ca7968deaa561a5c9e3cb04a904625e3ca10a95efc9c19a4d81a7e4219b3cc60211000000118d0de867000000000000000000

1 output(s) for total of 48.090065563000 dcy

stealth address amount amount idx
00: 9abeaf0e003996e952086e8d809b41af5d4656825d9afdf8a36048bd6fe57448 48.090065563000 688641 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": 333788, "vin": [ { "gen": { "height": 333778 } } ], "vout": [ { "amount": 48090065563, "target": { "key": "9abeaf0e003996e952086e8d809b41af5d4656825d9afdf8a36048bd6fe57448" } } ], "extra": [ 1, 156, 167, 150, 141, 234, 165, 97, 165, 201, 227, 203, 4, 169, 4, 98, 94, 60, 161, 10, 149, 239, 201, 193, 154, 77, 129, 167, 228, 33, 155, 60, 198, 2, 17, 0, 0, 0, 17, 141, 13, 232, 103, 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