Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 573845e99b71542ce61f84058523244009f4a1f0fdb4121474d5c0932a6e605c

Tx prefix hash: 0fd4da39f34274aa012cd47cd678b526ff7cf0ca948c48500175d981572b97cc
Tx public key: ad2a49ff951ad9c81ea82ca87ba1b49574a1e3d44c2e2289f3f2c2d775671cf9
Timestamp: 1726043022 Timestamp [UCT]: 2024-09-11 08:23:42 Age [y:d:h:m:s]: 00:118:02:01:08
Block: 1107658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84440 RingCT/type: yes/0
Extra: 01ad2a49ff951ad9c81ea82ca87ba1b49574a1e3d44c2e2289f3f2c2d775671cf9021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38f4c947437ee682efe842add47f1b61227dce5b62a700abaa1f4e0a60604df 0.600000000000 1585273 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": 1107668, "vin": [ { "gen": { "height": 1107658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38f4c947437ee682efe842add47f1b61227dce5b62a700abaa1f4e0a60604df" } } ], "extra": [ 1, 173, 42, 73, 255, 149, 26, 217, 200, 30, 168, 44, 168, 123, 161, 180, 149, 116, 161, 227, 212, 76, 46, 34, 137, 243, 242, 194, 215, 117, 103, 28, 249, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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