Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cd43df7ca8b83723ee90758272701e3446c31df6c6918a3c710b881ccaa709c

Tx prefix hash: 121028a1d1cfa85ca5bacd174e25d558cd86777c5144a55590c965eae582b655
Tx public key: fbcaca055a9a87cd4e33ec4405fe849e667abfd22e8c1e73fb27f2e293367bb8
Timestamp: 1713358022 Timestamp [UCT]: 2024-04-17 12:47:02 Age [y:d:h:m:s]: 00:358:19:55:33
Block: 1002490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256530 RingCT/type: yes/0
Extra: 01fbcaca055a9a87cd4e33ec4405fe849e667abfd22e8c1e73fb27f2e293367bb802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e396a7b8c743a55ca0c314e0eabcc2999c45598ec1d5678d0a502d84325d5e9 0.600000000000 1463006 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": 1002500, "vin": [ { "gen": { "height": 1002490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e396a7b8c743a55ca0c314e0eabcc2999c45598ec1d5678d0a502d84325d5e9" } } ], "extra": [ 1, 251, 202, 202, 5, 90, 154, 135, 205, 78, 51, 236, 68, 5, 254, 132, 158, 102, 122, 191, 210, 46, 140, 30, 115, 251, 39, 242, 226, 147, 54, 123, 184, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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