Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28444aa1a6b5446ebc3147952262a08159acf23c50855792020fa36edfb6f0f

Tx prefix hash: ef59f91657f35fd4c528411287efe67f0364833eaa79887fde696f28b3e14c12
Tx public key: 6eaab89f56452924e50f2a63539011a1c7d0f9cfada4a5b7f0f7d309a149d7de
Timestamp: 1737249133 Timestamp [UCT]: 2025-01-19 01:12:13 Age [y:d:h:m:s]: 00:305:05:38:41
Block: 1200375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215691 RingCT/type: yes/0
Extra: 016eaab89f56452924e50f2a63539011a1c7d0f9cfada4a5b7f0f7d309a149d7de02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 705a70ac9cb9a718d5b107d47f2dc53966ff3220186d83d3abb2890a66f6bd60 0.600000000000 1687018 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": 1200385, "vin": [ { "gen": { "height": 1200375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "705a70ac9cb9a718d5b107d47f2dc53966ff3220186d83d3abb2890a66f6bd60" } } ], "extra": [ 1, 110, 170, 184, 159, 86, 69, 41, 36, 229, 15, 42, 99, 83, 144, 17, 161, 199, 208, 249, 207, 173, 164, 165, 183, 240, 247, 211, 9, 161, 73, 215, 222, 2, 17, 0, 0, 0, 10, 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