Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb9f3bf8d7ce4774bab4a770252ac74be3c0a2a8aeff38422dcce0b49e13821

Tx prefix hash: ee0771cfc9f5be3fdbf286e62c7403a8abff4c74f47226b22f7dfb64e32f1df0
Tx public key: fab48488945d194834d660ece6b60feea2e55905b6d29c9cd972b3ad8d24423a
Timestamp: 1717820131 Timestamp [UCT]: 2024-06-08 04:15:31 Age [y:d:h:m:s]: 00:339:22:29:20
Block: 1039485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242961 RingCT/type: yes/0
Extra: 01fab48488945d194834d660ece6b60feea2e55905b6d29c9cd972b3ad8d24423a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea49e099f1d3f2b641a7c0075c6480287cbad4a246769a4c3afa995b43bd1737 0.600000000000 1508128 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": 1039495, "vin": [ { "gen": { "height": 1039485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea49e099f1d3f2b641a7c0075c6480287cbad4a246769a4c3afa995b43bd1737" } } ], "extra": [ 1, 250, 180, 132, 136, 148, 93, 25, 72, 52, 214, 96, 236, 230, 182, 15, 238, 162, 229, 89, 5, 182, 210, 156, 156, 217, 114, 179, 173, 141, 36, 66, 58, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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