Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296cecabec6e8616f2dccf932ffebabd6dd1d5e81dede951eea5c007984dce86

Tx prefix hash: aab669e8954ec8fc7c393913cee6b6bf91515ac94ffb2ec9cd45ff791860056e
Tx public key: c3f528beb5614791aea5bfbe4c4e6b60a013f85c9dfd1fe0cac190bd24fe33d9
Timestamp: 1730126142 Timestamp [UCT]: 2024-10-28 14:35:42 Age [y:d:h:m:s]: 00:158:08:05:06
Block: 1141437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112985 RingCT/type: yes/0
Extra: 01c3f528beb5614791aea5bfbe4c4e6b60a013f85c9dfd1fe0cac190bd24fe33d9021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac719b2930482bab1ce71253a09e604580f97500a928c6aa52a6eb2531eb0468 0.600000000000 1625244 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": 1141447, "vin": [ { "gen": { "height": 1141437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac719b2930482bab1ce71253a09e604580f97500a928c6aa52a6eb2531eb0468" } } ], "extra": [ 1, 195, 245, 40, 190, 181, 97, 71, 145, 174, 165, 191, 190, 76, 78, 107, 96, 160, 19, 248, 92, 157, 253, 31, 224, 202, 193, 144, 189, 36, 254, 51, 217, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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