Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82675c2cc7e25b4a3239f49305f6212d8b2c2d7229862dec68f9423119e857c

Tx prefix hash: ee05da7e82f3aaec30e7b64a9d95f5be5673855bf8d8008a0840960898203e38
Tx public key: a3c1b809651aaaeb3a61d0104b402f2192742bcf401b4258dd0ebc168aa60c40
Timestamp: 1696140705 Timestamp [UCT]: 2023-10-01 06:11:45 Age [y:d:h:m:s]: 01:097:21:58:03
Block: 859955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331255 RingCT/type: yes/0
Extra: 01a3c1b809651aaaeb3a61d0104b402f2192742bcf401b4258dd0ebc168aa60c4002110000000f4b8f5122000000000000000000

1 output(s) for total of 0.868184729000 dcy

stealth address amount amount idx
00: 6af6e304d757b4f14f479ce9c2869762ac10ac8b04f2e3e86dfc0603bab14bc8 0.868184729000 1314211 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": 859965, "vin": [ { "gen": { "height": 859955 } } ], "vout": [ { "amount": 868184729, "target": { "key": "6af6e304d757b4f14f479ce9c2869762ac10ac8b04f2e3e86dfc0603bab14bc8" } } ], "extra": [ 1, 163, 193, 184, 9, 101, 26, 170, 235, 58, 97, 208, 16, 75, 64, 47, 33, 146, 116, 43, 207, 64, 27, 66, 88, 221, 14, 188, 22, 138, 166, 12, 64, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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