Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f352b59dcc4771234a832bf6eebcca45544f9faa8670856c74d458bcdfb5aea0

Tx prefix hash: 496bd1e667f6e8d39f5e2780aeab6b09ac01204d09ba3ff7ec48a025b94fe6c1
Tx public key: 180675af4322d2a81210b29d41452fb105b4452f38eaf9c4b67b7aae81c7f89a
Timestamp: 1714973006 Timestamp [UCT]: 2024-05-06 05:23:26 Age [y:d:h:m:s]: 00:336:16:33:44
Block: 1015881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240654 RingCT/type: yes/0
Extra: 01180675af4322d2a81210b29d41452fb105b4452f38eaf9c4b67b7aae81c7f89a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46d366d04a7de3ca5f358f81e25d107976194200a6df0b38641f1aaba7c81934 0.600000000000 1479324 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": 1015891, "vin": [ { "gen": { "height": 1015881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46d366d04a7de3ca5f358f81e25d107976194200a6df0b38641f1aaba7c81934" } } ], "extra": [ 1, 24, 6, 117, 175, 67, 34, 210, 168, 18, 16, 178, 157, 65, 69, 47, 177, 5, 180, 69, 47, 56, 234, 249, 196, 182, 123, 122, 174, 129, 199, 248, 154, 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