Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0a0542261fdb2834ec8d99186efe7ff87c876f525a596b3289dcc2e9ea0b74

Tx prefix hash: d8880ba41cd36e5be821ca1a360ea2d8a31057c71fca09ab6030b2890f3ab044
Tx public key: 35dc70efd1d3906ef32f21f4e586a403466c59ffc05bd3f0eb345ad1dde930dc
Timestamp: 1708798476 Timestamp [UCT]: 2024-02-24 18:14:36 Age [y:d:h:m:s]: 01:258:01:40:08
Block: 964698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443167 RingCT/type: yes/0
Extra: 0135dc70efd1d3906ef32f21f4e586a403466c59ffc05bd3f0eb345ad1dde930dc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30fdd3ecbea4cd7c0414616407aa12d577ee26b0debad2e06137e2a10c0fc280 0.600000000000 1424441 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": 964708, "vin": [ { "gen": { "height": 964698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30fdd3ecbea4cd7c0414616407aa12d577ee26b0debad2e06137e2a10c0fc280" } } ], "extra": [ 1, 53, 220, 112, 239, 209, 211, 144, 110, 243, 47, 33, 244, 229, 134, 164, 3, 70, 108, 89, 255, 192, 91, 211, 240, 235, 52, 90, 209, 221, 233, 48, 220, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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