Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02741c08439482213634fa3801f01e8ea506970192271149a19cc29ee89a48e5

Tx prefix hash: 032778ff0b08d28f2b7b72dbf43946398d47166e8777f0a4ba6604349e138e60
Tx public key: 06c0571a91a3e16781706be417e2879f067ef86a6f6cb9fb1403e8d7c5733cda
Timestamp: 1728061085 Timestamp [UCT]: 2024-10-04 16:58:05 Age [y:d:h:m:s]: 00:110:10:24:53
Block: 1124395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78899 RingCT/type: yes/0
Extra: 0106c0571a91a3e16781706be417e2879f067ef86a6f6cb9fb1403e8d7c5733cda021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67a3cb2f79de234de1fe5cf82b8a34c31b987de687f41dc59d29bdff11bc7f1e 0.600000000000 1607014 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": 1124405, "vin": [ { "gen": { "height": 1124395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67a3cb2f79de234de1fe5cf82b8a34c31b987de687f41dc59d29bdff11bc7f1e" } } ], "extra": [ 1, 6, 192, 87, 26, 145, 163, 225, 103, 129, 112, 107, 228, 23, 226, 135, 159, 6, 126, 248, 106, 111, 108, 185, 251, 20, 3, 232, 215, 197, 115, 60, 218, 2, 17, 0, 0, 0, 1, 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