Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579f4b832bb005b3d5262236f70efb112b54e06dfba81c0f353b2743416f36ea

Tx prefix hash: 46d1580853a2b16f5dbda9a2f7396b66f607dd5ef1aed8bc7166f453ae57409f
Tx public key: f7ee8dc11bf2c99c5f48c876c4a711628c93eb3bcbbedde831c2e277750986fc
Timestamp: 1749249844 Timestamp [UCT]: 2025-06-06 22:44:04 Age [y:d:h:m:s]: 00:158:01:54:19
Block: 1299498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110665 RingCT/type: yes/0
Extra: 01f7ee8dc11bf2c99c5f48c876c4a711628c93eb3bcbbedde831c2e277750986fc021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b14f1afdab1836c1cf8dae74cc26b23270fd93796d752f42f0d957158bef2dc6 0.600000000000 1787035 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": 1299508, "vin": [ { "gen": { "height": 1299498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b14f1afdab1836c1cf8dae74cc26b23270fd93796d752f42f0d957158bef2dc6" } } ], "extra": [ 1, 247, 238, 141, 193, 27, 242, 201, 156, 95, 72, 200, 118, 196, 167, 17, 98, 140, 147, 235, 59, 203, 190, 221, 232, 49, 194, 226, 119, 117, 9, 134, 252, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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