Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f762300cb716420f4f6bca3fd9b2ef307917a792151c7149535476347a1b12ee

Tx prefix hash: 75e8203ce411208559b86ce145d5c16683179d4bda3071e46bf0e338dc79d455
Tx public key: 4f394d062eaf24ffb489ff99411c79b0a9c085cdc032a01ddf1821c11f3123a3
Timestamp: 1697169263 Timestamp [UCT]: 2023-10-13 03:54:23 Age [y:d:h:m:s]: 01:033:12:41:31
Block: 868476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285185 RingCT/type: yes/0
Extra: 014f394d062eaf24ffb489ff99411c79b0a9c085cdc032a01ddf1821c11f3123a30211000000024b8f5122000000000000000000

1 output(s) for total of 0.813539267000 dcy

stealth address amount amount idx
00: b0d73c8db522fe0e6110c77e4097391b522dce46cca76f97d0daa4df97d12bbb 0.813539267000 1323287 of 0

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": 868486, "vin": [ { "gen": { "height": 868476 } } ], "vout": [ { "amount": 813539267, "target": { "key": "b0d73c8db522fe0e6110c77e4097391b522dce46cca76f97d0daa4df97d12bbb" } } ], "extra": [ 1, 79, 57, 77, 6, 46, 175, 36, 255, 180, 137, 255, 153, 65, 28, 121, 176, 169, 192, 133, 205, 192, 50, 160, 29, 223, 24, 33, 193, 31, 49, 35, 163, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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