Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3b3b7830b03d641944b28c5cbb460c6c6a78b0ff57e61bd275f87cf0e3c0e1f

Tx prefix hash: 0cef197b5aeaa4d059d964a74ba13528e42f154fe0ae5302bc9c22d6fb483072
Tx public key: 1e2563ac24d6c7dd908ba8492c50365693b97432f4011df9385f000057b95243
Timestamp: 1695959238 Timestamp [UCT]: 2023-09-29 03:47:18 Age [y:d:h:m:s]: 01:213:12:03:41
Block: 858450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413668 RingCT/type: yes/0
Extra: 011e2563ac24d6c7dd908ba8492c50365693b97432f4011df9385f000057b9524302110000000575e3f0e9000000000000000000

1 output(s) for total of 0.878210923000 dcy

stealth address amount amount idx
00: d77b80bc7d3bef76a55f4e362d67d8009a93b5e4d59f982efc003e27b380f39e 0.878210923000 1312626 of 0

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": 858460, "vin": [ { "gen": { "height": 858450 } } ], "vout": [ { "amount": 878210923, "target": { "key": "d77b80bc7d3bef76a55f4e362d67d8009a93b5e4d59f982efc003e27b380f39e" } } ], "extra": [ 1, 30, 37, 99, 172, 36, 214, 199, 221, 144, 139, 168, 73, 44, 80, 54, 86, 147, 185, 116, 50, 244, 1, 29, 249, 56, 95, 0, 0, 87, 185, 82, 67, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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