Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f65d77cdd8d1e11125ebd2f1871f8b48435839612fff255d2864836cb480c6a

Tx prefix hash: 3735776d6fa9ca108c9d1aef7b63dd31e220b393da14e76c4d7fb7eabff1a32e
Tx public key: 29fab400e2376ad1e5a5cd97b3307f29bbb496c45e29e5a9ed94f52bbb6ed231
Timestamp: 1720870329 Timestamp [UCT]: 2024-07-13 11:32:09 Age [y:d:h:m:s]: 00:337:18:16:03
Block: 1064782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241261 RingCT/type: yes/0
Extra: 0129fab400e2376ad1e5a5cd97b3307f29bbb496c45e29e5a9ed94f52bbb6ed23102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c005de89fd01e5e90a165ec1399d465b87b60ddace76c8a19ffd75ac668e7eb5 0.600000000000 1535321 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": 1064792, "vin": [ { "gen": { "height": 1064782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c005de89fd01e5e90a165ec1399d465b87b60ddace76c8a19ffd75ac668e7eb5" } } ], "extra": [ 1, 41, 250, 180, 0, 226, 55, 106, 209, 229, 165, 205, 151, 179, 48, 127, 41, 187, 180, 150, 196, 94, 41, 229, 169, 237, 148, 245, 43, 187, 110, 210, 49, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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