Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5adcef0db171b3ea20126fdb51070de2146a9e0d3687d0cc4469522918896dc7

Tx prefix hash: d4fee09fae6ea5d2f4b7a4ee8e9e605c46ce8206770659d2e10bf3d9164f6868
Tx public key: 6979cb68285e5e67a5c21bb949a3f878c8b1765429c918d0841a9f77a3002b02
Timestamp: 1736831603 Timestamp [UCT]: 2025-01-14 05:13:23 Age [y:d:h:m:s]: 00:155:07:23:24
Block: 1196958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110700 RingCT/type: yes/0
Extra: 016979cb68285e5e67a5c21bb949a3f878c8b1765429c918d0841a9f77a3002b02021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0371e9a9bfb8129a0be4e2ed933ef4855ae432eaee2571097c8e785ce05cf32d 0.600000000000 1683563 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": 1196968, "vin": [ { "gen": { "height": 1196958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0371e9a9bfb8129a0be4e2ed933ef4855ae432eaee2571097c8e785ce05cf32d" } } ], "extra": [ 1, 105, 121, 203, 104, 40, 94, 94, 103, 165, 194, 27, 185, 73, 163, 248, 120, 200, 177, 118, 84, 41, 201, 24, 208, 132, 26, 159, 119, 163, 0, 43, 2, 2, 17, 0, 0, 0, 2, 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