Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd338210ddf6e4c5f742d79473a19b20d5927002f065d70c8d05bafaa8e0533

Tx prefix hash: 66c88f56122e0a214db64a991d91a14a2f9a1a0188810142da5c46f8edf8d930
Tx public key: 82f278b492d89c0a10f918b428d2b64aea871a9272ffb2418e3d1a4092892d82
Timestamp: 1748653219 Timestamp [UCT]: 2025-05-31 01:00:19 Age [y:d:h:m:s]: 00:174:23:01:33
Block: 1294567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122727 RingCT/type: yes/0
Extra: 0182f278b492d89c0a10f918b428d2b64aea871a9272ffb2418e3d1a4092892d8202110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7ff8993b0383a2785418ea08288d191a004e9185d3937233964a9ff709c76d 0.600000000000 1782062 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": 1294577, "vin": [ { "gen": { "height": 1294567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7ff8993b0383a2785418ea08288d191a004e9185d3937233964a9ff709c76d" } } ], "extra": [ 1, 130, 242, 120, 180, 146, 216, 156, 10, 16, 249, 24, 180, 40, 210, 182, 74, 234, 135, 26, 146, 114, 255, 178, 65, 142, 61, 26, 64, 146, 137, 45, 130, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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