Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b80f11896024747642264219ff4ea7a2d8265f36f02612eb540b559128416073

Tx prefix hash: c4719787331bd2e9e2df2563586e243fac7096108d30d06cf4edf03bf4e0bd8e
Tx public key: cc1f6dcaae9028726f904daa3c3945692778e07ca777a9d01f4bb1d3edefedf0
Timestamp: 1744337922 Timestamp [UCT]: 2025-04-11 02:18:42 Age [y:d:h:m:s]: 00:222:07:19:35
Block: 1258829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156603 RingCT/type: yes/0
Extra: 01cc1f6dcaae9028726f904daa3c3945692778e07ca777a9d01f4bb1d3edefedf00211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0db4f5f0a66d20d07cac8bef6c34d83b7e3291359fcc2af52893c97e841bbcc 0.600000000000 1745966 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": 1258839, "vin": [ { "gen": { "height": 1258829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0db4f5f0a66d20d07cac8bef6c34d83b7e3291359fcc2af52893c97e841bbcc" } } ], "extra": [ 1, 204, 31, 109, 202, 174, 144, 40, 114, 111, 144, 77, 170, 60, 57, 69, 105, 39, 120, 224, 124, 167, 119, 169, 208, 31, 75, 177, 211, 237, 239, 237, 240, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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