Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287cf26c686642ebd7789b316035f80d1ea9087884fd9e3ef007a16eee97170c

Tx prefix hash: 4d263b5ccf3a0f2e4fb9b1f2842e6627752557b6af54873be1fbb42b08a347a1
Tx public key: 6dababf176087e8f747d3042ce0a064079b3848fcad3c917b96e26848a80e6af
Timestamp: 1724348187 Timestamp [UCT]: 2024-08-22 17:36:27 Age [y:d:h:m:s]: 00:238:03:42:58
Block: 1093611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170063 RingCT/type: yes/0
Extra: 016dababf176087e8f747d3042ce0a064079b3848fcad3c917b96e26848a80e6af021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b480b9d5fd206638f8d5570c55cb214a316a9560293e0ffbee0f56e118e5c9d 0.600000000000 1568590 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": 1093621, "vin": [ { "gen": { "height": 1093611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b480b9d5fd206638f8d5570c55cb214a316a9560293e0ffbee0f56e118e5c9d" } } ], "extra": [ 1, 109, 171, 171, 241, 118, 8, 126, 143, 116, 125, 48, 66, 206, 10, 6, 64, 121, 179, 132, 143, 202, 211, 201, 23, 185, 110, 38, 132, 138, 128, 230, 175, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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