Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0def1b006df212f2caedcf918bbbd51d1b4486d7ee1b820bfa9229baf8742e

Tx prefix hash: f0dd230483ca2fe35954e089fe7a4348609b7ce5bfb44bf8b5a9ada8fa6a1d8b
Tx public key: 9f1cd16a66affd145f020e6be1a0d54496a943579b642100ae204ca5f7c86f4a
Timestamp: 1687256437 Timestamp [UCT]: 2023-06-20 10:20:37 Age [y:d:h:m:s]: 01:292:08:37:17
Block: 786344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470109 RingCT/type: yes/0
Extra: 019f1cd16a66affd145f020e6be1a0d54496a943579b642100ae204ca5f7c86f4a021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.522355396000 dcy

stealth address amount amount idx
00: 864d2f7545d01c902991c98164a9cc044e546ca74a05d9243c29deeaf1a58647 1.522355396000 1236329 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": 786354, "vin": [ { "gen": { "height": 786344 } } ], "vout": [ { "amount": 1522355396, "target": { "key": "864d2f7545d01c902991c98164a9cc044e546ca74a05d9243c29deeaf1a58647" } } ], "extra": [ 1, 159, 28, 209, 106, 102, 175, 253, 20, 95, 2, 14, 107, 225, 160, 213, 68, 150, 169, 67, 87, 155, 100, 33, 0, 174, 32, 76, 165, 247, 200, 111, 74, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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