Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6adeb7853439656d31b2e4c70e849cb3b9e08934895d3b6ffbc2e4a6c69c6f0

Tx prefix hash: 33982112ad0d08efa1a7a4ff8dc16cba41e22bfe8c53403804f96789b265a070
Tx public key: ecddb006a1aaa5e6bae6b0aa6b59306d986f5437f0a94ea6575137021474b041
Timestamp: 1676446343 Timestamp [UCT]: 2023-02-15 07:32:23 Age [y:d:h:m:s]: 02:100:11:38:41
Block: 697362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593453 RingCT/type: yes/0
Extra: 01ecddb006a1aaa5e6bae6b0aa6b59306d986f5437f0a94ea6575137021474b04102110000000a5029cbac000000000000000000

1 output(s) for total of 3.001581379000 dcy

stealth address amount amount idx
00: deb3f5f3333ed71645cbdd75e5b9903a93763933fefa6c653869627d1687993c 3.001581379000 1140521 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": 697372, "vin": [ { "gen": { "height": 697362 } } ], "vout": [ { "amount": 3001581379, "target": { "key": "deb3f5f3333ed71645cbdd75e5b9903a93763933fefa6c653869627d1687993c" } } ], "extra": [ 1, 236, 221, 176, 6, 161, 170, 165, 230, 186, 230, 176, 170, 107, 89, 48, 109, 152, 111, 84, 55, 240, 169, 78, 166, 87, 81, 55, 2, 20, 116, 176, 65, 2, 17, 0, 0, 0, 10, 80, 41, 203, 172, 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