Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eaece8bf27a76b0ca41ac295cc5af3d28fcb5fff5b66cd5520fa410ede6eb2a

Tx prefix hash: ae3a4713c9b7dbecb202c74ce5b3d1d4fc2a9ed2c5e4360a616973dd47c806cd
Tx public key: b23324af8db071bbedab749f8330beed154618cdd87c0e27ecb30f833d59a0b2
Timestamp: 1709373670 Timestamp [UCT]: 2024-03-02 10:01:10 Age [y:d:h:m:s]: 01:084:01:20:12
Block: 969465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321116 RingCT/type: yes/0
Extra: 01b23324af8db071bbedab749f8330beed154618cdd87c0e27ecb30f833d59a0b20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f53322c59ab23c84d77fdd6efcd8ca6e6ca3086c1e645c823df9f1a13ed7b3d4 0.600000000000 1429298 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": 969475, "vin": [ { "gen": { "height": 969465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f53322c59ab23c84d77fdd6efcd8ca6e6ca3086c1e645c823df9f1a13ed7b3d4" } } ], "extra": [ 1, 178, 51, 36, 175, 141, 176, 113, 187, 237, 171, 116, 159, 131, 48, 190, 237, 21, 70, 24, 205, 216, 124, 14, 39, 236, 179, 15, 131, 61, 89, 160, 178, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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