Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6f1c4d9dcca45d8416bf952828fe095014969541801ebaf8cfbf6da2b0ec8d

Tx prefix hash: 27e3e7411094dc9688c512d6356b4e0d9f72330684cab0925107ea8154aebe58
Tx public key: 950d66cc81179f08c5b11fbd331d2155c5c8b036d7ddf133df373c16d923b6f3
Timestamp: 1761260970 Timestamp [UCT]: 2025-10-23 23:09:30 Age [y:d:h:m:s]: 00:096:17:37:33
Block: 1396525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69067 RingCT/type: yes/0
Extra: 01950d66cc81179f08c5b11fbd331d2155c5c8b036d7ddf133df373c16d923b6f3021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f06a7766cc663425c3c11368f63f2495aae4e1f9442e05e0ceaaf515cf322f96 0.600000000000 1884812 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": 1396535, "vin": [ { "gen": { "height": 1396525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f06a7766cc663425c3c11368f63f2495aae4e1f9442e05e0ceaaf515cf322f96" } } ], "extra": [ 1, 149, 13, 102, 204, 129, 23, 159, 8, 197, 177, 31, 189, 51, 29, 33, 85, 197, 200, 176, 54, 215, 221, 241, 51, 223, 55, 60, 22, 217, 35, 182, 243, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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