Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a93897f42fff2ea78ddb792653f07e229a081433828052c148914c7df86435

Tx prefix hash: 725d3d90bc7fbe77afe4a07567b2ed40a4cf77a719d21913a7ccf0705107b519
Tx public key: 57c862675764e9108ed3c7c0d77bee074618d59485793f4b6a60d126127691d1
Timestamp: 1747201530 Timestamp [UCT]: 2025-05-14 05:45:30 Age [y:d:h:m:s]: 00:188:14:38:49
Block: 1282540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132498 RingCT/type: yes/0
Extra: 0157c862675764e9108ed3c7c0d77bee074618d59485793f4b6a60d126127691d102110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 070e63b2bbb1db9d0e5ac932ea867916e5bcee81bae5d0e9b939413974e8adce 0.600000000000 1769947 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": 1282550, "vin": [ { "gen": { "height": 1282540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070e63b2bbb1db9d0e5ac932ea867916e5bcee81bae5d0e9b939413974e8adce" } } ], "extra": [ 1, 87, 200, 98, 103, 87, 100, 233, 16, 142, 211, 199, 192, 215, 123, 238, 7, 70, 24, 213, 148, 133, 121, 63, 75, 106, 96, 209, 38, 18, 118, 145, 209, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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