Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df2720987d399a54e8f11ed1cffcb112a9ce847b3a82017823a3cc7b22c0224

Tx prefix hash: 4a33b8b6f089e6dc58cdbc1e12860b9f6cdf310e3e8315947c953cf3a48c7d2d
Tx public key: d5567854424c972583a958b89acd922ec586e87d27ef7f06195b196a1c07b2a6
Timestamp: 1735769494 Timestamp [UCT]: 2025-01-01 22:11:34 Age [y:d:h:m:s]: 00:130:23:56:26
Block: 1188157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93435 RingCT/type: yes/0
Extra: 01d5567854424c972583a958b89acd922ec586e87d27ef7f06195b196a1c07b2a6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f52c785f0f17b67a59170a744e9c40422d64e8cd507ffbcdcffe0665f739aca0 0.600000000000 1674658 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": 1188167, "vin": [ { "gen": { "height": 1188157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f52c785f0f17b67a59170a744e9c40422d64e8cd507ffbcdcffe0665f739aca0" } } ], "extra": [ 1, 213, 86, 120, 84, 66, 76, 151, 37, 131, 169, 88, 184, 154, 205, 146, 46, 197, 134, 232, 125, 39, 239, 127, 6, 25, 91, 25, 106, 28, 7, 178, 166, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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