Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9c6f93588ee788f85d29a69ec092eb72d510d75f46f65375a90fa99dad480a

Tx prefix hash: bd20665c8be12f16bf8f56555bfd5e5d795b313724d82be8d54939d826b461db
Tx public key: 1a3694c6a9848cfd98280b7fb40ed7e479d9a63d18b43be40c13dd09f90c99b9
Timestamp: 1719621641 Timestamp [UCT]: 2024-06-29 00:40:41 Age [y:d:h:m:s]: 00:280:06:15:24
Block: 1054416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200259 RingCT/type: yes/0
Extra: 011a3694c6a9848cfd98280b7fb40ed7e479d9a63d18b43be40c13dd09f90c99b90211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39b12d70c3dc7b4a5f6754af1743ec7a1752e2ce186a9dcf1bc0f5a79a289bf4 0.600000000000 1524777 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": 1054426, "vin": [ { "gen": { "height": 1054416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39b12d70c3dc7b4a5f6754af1743ec7a1752e2ce186a9dcf1bc0f5a79a289bf4" } } ], "extra": [ 1, 26, 54, 148, 198, 169, 132, 140, 253, 152, 40, 11, 127, 180, 14, 215, 228, 121, 217, 166, 61, 24, 180, 59, 228, 12, 19, 221, 9, 249, 12, 153, 185, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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