Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab86c2b0de3566bd73460c5b7bba26e8ee98f2fcde2b2fd6770725cd3d68a9ac

Tx prefix hash: 6bb5cbded5998b605f021d49d023826f4693198318eae98029f2fba9c92e8ba5
Tx public key: 073490c3834271adb41a46faf54cf2ab3a30e4cc66c0d5b6a8dca41bf040eb07
Timestamp: 1750352509 Timestamp [UCT]: 2025-06-19 17:01:49 Age [y:d:h:m:s]: 00:155:04:15:25
Block: 1308497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108717 RingCT/type: yes/0
Extra: 01073490c3834271adb41a46faf54cf2ab3a30e4cc66c0d5b6a8dca41bf040eb0702110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441495370de94061f48d20c5a1e381a066eb0c5f3e3309ea8d209f9019740557 0.600000000000 1796110 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": 1308507, "vin": [ { "gen": { "height": 1308497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441495370de94061f48d20c5a1e381a066eb0c5f3e3309ea8d209f9019740557" } } ], "extra": [ 1, 7, 52, 144, 195, 131, 66, 113, 173, 180, 26, 70, 250, 245, 76, 242, 171, 58, 48, 228, 204, 102, 192, 213, 182, 168, 220, 164, 27, 240, 64, 235, 7, 2, 17, 0, 0, 0, 6, 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