Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da8ba3b3c8b827a5c5979e66cd0508494b143971ddc1dda0f7264b14901f2baa

Tx prefix hash: 60d421252a104de71118920bd70848f9a67178497a380846472c6f866ce2be2a
Tx public key: 642c02ce8279cc36dc7ea0aa1cbf3648007bced1aad20f9154dce6a67a14c1d3
Timestamp: 1574700947 Timestamp [UCT]: 2019-11-25 16:55:47 Age [y:d:h:m:s]: 05:170:05:42:18
Block: 17283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264320 RingCT/type: yes/0
Extra: 01642c02ce8279cc36dc7ea0aa1cbf3648007bced1aad20f9154dce6a67a14c1d302110000000ab63f0b49000000000000000000

1 output(s) for total of 537.941596204000 dcy

stealth address amount amount idx
00: 5f326a80caf2c9dc61be06e38f3d3734856dffa3314fab553ca70f740603b06a 537.941596204000 24921 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": 17293, "vin": [ { "gen": { "height": 17283 } } ], "vout": [ { "amount": 537941596204, "target": { "key": "5f326a80caf2c9dc61be06e38f3d3734856dffa3314fab553ca70f740603b06a" } } ], "extra": [ 1, 100, 44, 2, 206, 130, 121, 204, 54, 220, 126, 160, 170, 28, 191, 54, 72, 0, 123, 206, 209, 170, 210, 15, 145, 84, 220, 230, 166, 122, 20, 193, 211, 2, 17, 0, 0, 0, 10, 182, 63, 11, 73, 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