Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a9717fbf99ab5260bcc1c5983a236bce18c69830b46f6a187cb3c250f927e59

Tx prefix hash: b8e8cd49cf94820bfefef040069bb35b3caf1509ad7ff467b467afca66004f89
Tx public key: f9c14f810e4e0b3333c794a8c326b750756a3a7d9923d5f87a972bcaab25241a
Timestamp: 1737065151 Timestamp [UCT]: 2025-01-16 22:05:51 Age [y:d:h:m:s]: 00:151:23:17:03
Block: 1198887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108318 RingCT/type: yes/0
Extra: 01f9c14f810e4e0b3333c794a8c326b750756a3a7d9923d5f87a972bcaab25241a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ddbf065e6ac40e0f9126045a0180257f202840c17f3bf6f885508a1f83f4397 0.600000000000 1685514 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": 1198897, "vin": [ { "gen": { "height": 1198887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ddbf065e6ac40e0f9126045a0180257f202840c17f3bf6f885508a1f83f4397" } } ], "extra": [ 1, 249, 193, 79, 129, 14, 78, 11, 51, 51, 199, 148, 168, 195, 38, 183, 80, 117, 106, 58, 125, 153, 35, 213, 248, 122, 151, 43, 202, 171, 37, 36, 26, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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