Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a26dfbc1fb60af220abacc40a3d5b468c3b9ab78e4562609a0b8972f3a437d9

Tx prefix hash: 7048542b148a0ae3303259f5d8362f2a9d8e4bcf8f7a1457651bfdaf51835c5c
Tx public key: 244856811ff634b74206e56af48cca319ed79aa0dc2f6a45553a6cbccdbef489
Timestamp: 1722937553 Timestamp [UCT]: 2024-08-06 09:45:53 Age [y:d:h:m:s]: 00:245:08:44:06
Block: 1081905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175253 RingCT/type: yes/0
Extra: 01244856811ff634b74206e56af48cca319ed79aa0dc2f6a45553a6cbccdbef48902110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0939f29aaf3e4c315aa6ae2b8de132e7811c59d73521e66a5481d728c76c02a0 0.600000000000 1555728 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": 1081915, "vin": [ { "gen": { "height": 1081905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0939f29aaf3e4c315aa6ae2b8de132e7811c59d73521e66a5481d728c76c02a0" } } ], "extra": [ 1, 36, 72, 86, 129, 31, 246, 52, 183, 66, 6, 229, 106, 244, 140, 202, 49, 158, 215, 154, 160, 220, 47, 106, 69, 85, 58, 108, 188, 205, 190, 244, 137, 2, 17, 0, 0, 0, 12, 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