Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6f3983d2178496b11ebf85d01b8bc7b1ec1d732e1970de32d4c188808cf10c1

Tx prefix hash: 56870615222070c76a3cde16d9299365cc6cab9670a95b7a39d618f13c61ee7a
Tx public key: 434e0760cafd8e3edb31eac519ffdcfe8fc1c874b29df329ca8077d51d66bccb
Timestamp: 1738482181 Timestamp [UCT]: 2025-02-02 07:43:01 Age [y:d:h:m:s]: 00:361:10:43:48
Block: 1210354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256003 RingCT/type: yes/0
Extra: 01434e0760cafd8e3edb31eac519ffdcfe8fc1c874b29df329ca8077d51d66bccb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ff58c1308cc6eb3a192a453eff95fb4a235a4272a432786d178295a24d2367d 0.600000000000 1697105 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": 1210364, "vin": [ { "gen": { "height": 1210354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff58c1308cc6eb3a192a453eff95fb4a235a4272a432786d178295a24d2367d" } } ], "extra": [ 1, 67, 78, 7, 96, 202, 253, 142, 62, 219, 49, 234, 197, 25, 255, 220, 254, 143, 193, 200, 116, 178, 157, 243, 41, 202, 128, 119, 213, 29, 102, 188, 203, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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