Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcec26761f5b4fed6adcc10684dd10dfff521c8f8da708761e088d2bb7e954bc

Tx prefix hash: 6d064118b6e3d24a379c0f91d8ebe9e877dd924f7ef0e819811d7e33c4556b9a
Tx public key: 978acfe810e47ba40ed0086fda0ee4c03e748a299df1fa5aa595adc919041b17
Timestamp: 1582522274 Timestamp [UCT]: 2020-02-24 05:31:14 Age [y:d:h:m:s]: 04:307:06:38:11
Block: 71601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111983 RingCT/type: yes/0
Extra: 01978acfe810e47ba40ed0086fda0ee4c03e748a299df1fa5aa595adc919041b17021100000003026b59f3000000000000000000

1 output(s) for total of 355.432360122000 dcy

stealth address amount amount idx
00: 6ce3cbbe5fda70230720b7d0efb0d7b154c9069bd306f97249004b4eea578953 355.432360122000 132182 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": 71611, "vin": [ { "gen": { "height": 71601 } } ], "vout": [ { "amount": 355432360122, "target": { "key": "6ce3cbbe5fda70230720b7d0efb0d7b154c9069bd306f97249004b4eea578953" } } ], "extra": [ 1, 151, 138, 207, 232, 16, 228, 123, 164, 14, 208, 8, 111, 218, 14, 228, 192, 62, 116, 138, 41, 157, 241, 250, 90, 165, 149, 173, 201, 25, 4, 27, 23, 2, 17, 0, 0, 0, 3, 2, 107, 89, 243, 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