Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa35d81563c8a4ba9ea655c7ecd3161d261f66803fb625ee16df386f8a51947

Tx prefix hash: dce4f598842672ed4d87d41e3ea95b2a8ae4f87e927990b25774f97aeba89779
Tx public key: 41e08548d8c5180d6f4475340cf907831c15613f19805ea905c51d802a0424ad
Timestamp: 1690993466 Timestamp [UCT]: 2023-08-02 16:24:26 Age [y:d:h:m:s]: 01:272:16:31:07
Block: 817342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455980 RingCT/type: yes/0
Extra: 0141e08548d8c5180d6f4475340cf907831c15613f19805ea905c51d802a0424ad02110000000c33af99f4000000000000000000

1 output(s) for total of 1.201729614000 dcy

stealth address amount amount idx
00: feb96183b91413e4fed2f889cc58fd1e1f3a3ac59c3cac1a489005c92d3e9a16 1.201729614000 1269242 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": 817352, "vin": [ { "gen": { "height": 817342 } } ], "vout": [ { "amount": 1201729614, "target": { "key": "feb96183b91413e4fed2f889cc58fd1e1f3a3ac59c3cac1a489005c92d3e9a16" } } ], "extra": [ 1, 65, 224, 133, 72, 216, 197, 24, 13, 111, 68, 117, 52, 12, 249, 7, 131, 28, 21, 97, 63, 25, 128, 94, 169, 5, 197, 29, 128, 42, 4, 36, 173, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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