Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f66e66e98dcdd90a03fd5843363df0cb90a5470098c869da5c7d36bdbc9dc271

Tx prefix hash: 69904c34d94e8e98d55e49aef71cef62a09f1733e3a89af0592de8f81ace13f8
Tx public key: a7c930b4c63b182556eb461735c84172f0a5a6b689b42733f35ef50a54bbd079
Timestamp: 1737092085 Timestamp [UCT]: 2025-01-17 05:34:45 Age [y:d:h:m:s]: 00:151:19:28:54
Block: 1199109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108201 RingCT/type: yes/0
Extra: 01a7c930b4c63b182556eb461735c84172f0a5a6b689b42733f35ef50a54bbd07902110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13c4400d2b0472bf753336fdde4a922f487cbf0f947d05a8795d228215deed1f 0.600000000000 1685738 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": 1199119, "vin": [ { "gen": { "height": 1199109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13c4400d2b0472bf753336fdde4a922f487cbf0f947d05a8795d228215deed1f" } } ], "extra": [ 1, 167, 201, 48, 180, 198, 59, 24, 37, 86, 235, 70, 23, 53, 200, 65, 114, 240, 165, 166, 182, 137, 180, 39, 51, 243, 94, 245, 10, 84, 187, 208, 121, 2, 17, 0, 0, 0, 15, 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