Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793731d3cf1e5110cbd740d2d9a3b09107a2bdfee0ea865460923d73235171da

Tx prefix hash: 01f214f9d20a9b576fdc36a4d6e666d9e5a34351c5f9849ed3abfae2e947934f
Tx public key: b2508b39673e2600d03237228eed0e644def6986b78611de2bdb1f536f8d48c9
Timestamp: 1695947211 Timestamp [UCT]: 2023-09-29 00:26:51 Age [y:d:h:m:s]: 01:174:21:46:53
Block: 858350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386054 RingCT/type: yes/0
Extra: 01b2508b39673e2600d03237228eed0e644def6986b78611de2bdb1f536f8d48c902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.878881203000 dcy

stealth address amount amount idx
00: 55e1349ac73aa5f87c60f9b2cd24b73b6979d49ba677a103a587f5894ad1581c 0.878881203000 1312520 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": 858360, "vin": [ { "gen": { "height": 858350 } } ], "vout": [ { "amount": 878881203, "target": { "key": "55e1349ac73aa5f87c60f9b2cd24b73b6979d49ba677a103a587f5894ad1581c" } } ], "extra": [ 1, 178, 80, 139, 57, 103, 62, 38, 0, 208, 50, 55, 34, 142, 237, 14, 100, 77, 239, 105, 134, 183, 134, 17, 222, 43, 219, 31, 83, 111, 141, 72, 201, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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