Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a08ca9ba9d3969b7cbb82095c3c3ecd68899286e16feb54cdc5d9ac3b778be04

Tx prefix hash: 8340cbd19db5ec12673a7cf92b4661e44c489f99cfe48398d04f6bcb02eefc65
Tx public key: b9f0e841c168cd0d3987341562ea9ef2b59f61a31e60fcd6674cde5b07f997f8
Timestamp: 1735839748 Timestamp [UCT]: 2025-01-02 17:42:28 Age [y:d:h:m:s]: 00:321:20:47:41
Block: 1188743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227545 RingCT/type: yes/0
Extra: 01b9f0e841c168cd0d3987341562ea9ef2b59f61a31e60fcd6674cde5b07f997f80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0454bf5347fc0790b1fdf471dd1ec43ad8f261774ca6df1f7bc9346f3528946f 0.600000000000 1675246 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": 1188753, "vin": [ { "gen": { "height": 1188743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0454bf5347fc0790b1fdf471dd1ec43ad8f261774ca6df1f7bc9346f3528946f" } } ], "extra": [ 1, 185, 240, 232, 65, 193, 104, 205, 13, 57, 135, 52, 21, 98, 234, 158, 242, 181, 159, 97, 163, 30, 96, 252, 214, 103, 76, 222, 91, 7, 249, 151, 248, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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